Common Object Properties
This topic describes the common object properties supported across multiple databases in Quest Data Modeler. While each database can expose additional or database‑specific options, the core properties described here are applicable to most relational and analytical platforms.
The following section describes how to create an object and access its properties in the Quick Editor, where you can set the common properties listed in this topic.
Note: You can use the Ctrl+Z and Ctrl+Y keyboard shortcuts to undo and redo changes in any property field.
Creating Objects and Defining Object Properties
To create objects and define their properties:
-
In the Model Explorer, select
on the object, and then select Create New.An instance of the object is created.
-
On the new object, select
, and then select Properties. You can also double-click the object in the diagram or Model Explorer to access properties.The Quick Editor opens and displays the object properties tabs.
-
Set the required property values.
-
Select Close.
The following table describes the common properties available across most objects.
| Tab | Section | Property | Description | Additional Properties |
|---|---|---|---|---|
| Properties | General | Name | Specifies the name of the object | |
| Physical Name | Specifies the physical name of the object | |||
| Harden Strategy | Specifies the name of the hardening strategy for a table |
|
||
| Comments | Specifies the comment added by the user | |||
| Update Entity Definition to Match | Specifies the comments in an object to appear as a definition for the corresponding entity | |||
| Physical Only | Specifies whether the object is suppressed from a logical model and appears in a physical model only | |||
| Initial Row Count | Specifies an initial number of records for the selected table | |||
| Max Rows | Specifies the maximum allowable number of records that the object is designed to hold. You can leave this field empty to achieve open-ended growth. This option and the Grow By Month option determine when an object will reach its designed record limit. | |||
| Growth By Month | Specifies the estimated number of records that you expect the object to grow per month. If you have a maximum record number in the Max Rows field, object growth will stop at that record number | |||
| Comment | Comment | Specifies the comment added by the user for the object. Use the toolbar to cut, copy, or paste text, restore inheritance from definition, work with the Text Editor, download, or run a spell check. | If your target server supports comments, you can generate comments in the schema DDL script. | |
| Update Entity Definition To Match | Specifies whether to update the entity definition to match comments | |||
| Where Used | Name | Specifies the name of the object used by the selected object in the editor | ||
| Type | Specifies the object type | |||
| Parent | Specifies the parent object of the selected object | |||
| Parent Type | Specifies the parent object type | |||
| UDP | Name | Specifies the name of the UDP | ||
| Data Type | Specifies the UDP datatype |
Select the cell and select one of the following datatypes from the drop-down:
|
||
| Values List | Specifies selectable values | |||
| Default Value | Specifies a user-defined property default value when applicable | |||
| Description | Specifies a description for the UDP | |||
| Business Terms Mapping | Name | Specifies the name of the business term | ||
| Definition | Specifies the definition of the business term | |||
| Description | Specifies the description of the business term | |||
| SDI | Sensitive Data Indicator (SDI), specifies whether the asset is sensitive | |||
| SDI Classification | Specifies the SDI classification of the asset | |||
| Path | Specifies the asset path | |||
| History | Event | Specifies the history events that you have selected to track for the model or object | ||
| Description | Specifies the description of the event | |||
| Source Path | Specifies the source of the object. The Source Path column is empty for the Create event. Source Path is formatted as follows:
$ModelPath\<$ModelName>\$EntityName\$AttributeName $ModelPath is the path for a model in the Mart Portal. |
|||
| Comment | Specifies the notes entered by the user | |||
| Date Created | Specifies the date and time the event was created | |||
| Created By | Specifies the name of the user that created the event | |||
| Notes | Event | Specifies the note events that you have selected to track for the model or object | ||
| Comment | Specifies the comment that is entered in the Notes tab | |||
| Date Created | Specifies the date and time of the created note | |||
| Created By | Specifies the name of the user that created the note | |||
| Date Updated | Specifies the date and time of the updated note | |||
| Updated By | Specifies the name of the user who updated the note | |||
| Extended Notes | Name | Specifies the name of the extended note | ||
| Event | Specifies the extended events that you have selected to track for the model or object | |||
| Comments | Specifies the user's note | |||
| Modified By | Specifies the name of the user that modified the extended note | |||
| Importance | Specifies the importance that you would like to provide to the extended note | |||
| Note Status | Specifies the status of the extended note | |||
| Date Modified | Specifies the date and time of the modified extended note |
User-Defined Properties
You can define custom properties and assign them to different classes of model objects. User-defined properties (UDPs) help document and describe logical and physical object classes.
A user-defined property can be any value that you consider useful for managing a specific object class. For example, as a database administrator (DBA) in a team environment where multiple developers maintain many tables, you can create a user-defined property in the Table Editor that lets each developer select their name to indicate responsibility for a table.
You can assign UDPs to any object class in its editor. Each object editor includes a UDP tab that lets you assign UDPs. The UDP tab works the same way in all editors. You can view each UDP name and add values.
Adding a User-Defined Property to a Physical Object
To add a user-defined property to a physical object:
- Open Quick Editor for the physical object for which you want to add a user-defined property.
-
Select the UDP tab, and then select
.
- The User Defined Properties page opens. You can add, edit, or delete UDPs based on their classes.
- Select New Property to add a new UDP.
- Enter name, data type, values, and description as required.
- Select Close.
User-defined propertie is created and the User Defined Properties dialog closes.
Although Quest Data Modeler provides a unified experience, each database can support additional properties or impose restrictions that are not common across all platforms.
For database-specific behavior, refer to the individual database support topics listed under Database and API Support.